feat(gen2-migration): add migration support for overriding default reso…#14761
Closed
dgandhi62 wants to merge 12 commits intogen2-migrationfrom
Closed
feat(gen2-migration): add migration support for overriding default reso…#14761dgandhi62 wants to merge 12 commits intogen2-migrationfrom
dgandhi62 wants to merge 12 commits intogen2-migrationfrom
Conversation
…lvers When a Gen1 project has custom VTL resolver files in amplify/backend/api/<name>/resolvers/, the DataGenerator now: - Detects .vtl files in the local resolvers directory - Copies them to amplify/data/resolvers/ in the Gen2 output - Generates backend.ts code that reads the VTL files at runtime and overrides pipeline function request/response mapping templates, replacing S3-based templates with inline content Supports both .req.vtl (request) and .res.vtl (response) resolver overrides. The generated for-of loop determines the resolver type from the filename suffix and overrides the corresponding mapping template properties.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
When a Gen1 project has custom VTL resolver files in
amplify/backend/api/<name>/resolvers/, the migration tool now detects them, copies them toamplify/data/resolvers/in the Gen2 output, and generatesbackend.tscode that overrides the pipeline function mapping templates at runtime.Gen1 and Gen2 both use pipeline resolvers. The generated code reads VTL files from
data/resolvers/, looks up the correspondingcfnFunctionConfigurationsentry by convention (${typeName}${FieldName}DataResolverFn), clears the S3 template location, and sets the inline template content instead. Both request (.req.vtl) and response (.res.vtl) overrides are supported.EXPECTED OUTPUT
Along with a copied
resolversdirectory